Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@shopify/async
Advanced tools
@shopify/async
Primitives for loading parts of an application asynchronously.
$ yarn add @shopify/async
This package provides a wrapper for asynchronous import statements that allows for synchronous resolution and cacheing. This wrapper can be created using the createResolver
function. The resulting Resolver
object exposes a number of methods for interacting with the loaded module.
const resolver = createResolver({
load: () => import('./expensive'),
});
// Access the resolved module, if available. If an `id` option is provided
// to `createResolver`, the resolver will attempt to synchronously
// resolve the module based on the environment and the passed identifier.
resolver.resolved;
// If you provide an `id` option to `createResolver`, it will be
// reflected here
resolver.id;
// Force the module to resolve. Returns a promise for the resolved value.
resolver.resolve();
This package also contains a few types that are useful for creating async components:
Import
represents a value that could be default or non-default exportDeferTiming
is an enum of defer timing values; has values for component Mount
, browser Idle
, or element InViewport
As well as the following types related to window.requestIdleCallback
:
RequestIdleCallbackHandle
RequestIdleCallbackOptions
RequestIdleCallbackDeadline
RequestIdleCallback
WindowWithRequestIdleCallback
Finally, this package includes a plugin for Babel that allows the module IDs that are asynchronously imported to be exposed to the application.
The Babel plugin is exported from the @shopify/async/babel
entrypoint. This plugin will look for any functions imported from the specified packages. It will then iterate over each reference to that function and, if the reference is a call expression where the first argument is an object, and that object has a load
function, will mark it for processing. The adjustment is simple: it simply adds an id
method that returns a Webpack-specific identifier based on the first dynamic import in the load
method, allowing the function to use this identifier to mark the module as used.
import {createAsyncComponent} from 'my-package';
createAsyncComponent({
load: () => import('../SomeComponent'),
});
// Becomes:
createAsyncComponent({
load: () => import('../SomeComponent'),
id: () => require.resolveWeak('../SomeComponent'),
});
packages
packages
should be an object where the keys are the names of packages, and the values are an array of functions that should be processed. This option defaults to an object containing a few Shopify-specific async packages (createAsyncComponent
and createAsyncContext
from @shopify/react-async
, and createAsyncQueryComponent
from @shopify/react-graphql
).
// babel.config.js
{
plugins: [
['@shopify/async/babel', {
packages: {
'my-package': ['createAsyncComponent'],
},
}],
],
}
webpack
If you are using your components in a non-Webpack environment (for example, in Jest), you can pass the webpack: false
option to this plugin. This disables the Webpack-specific require.resolveWeak
addition, and instead uses require.resolve
. The resulting id
can then be used to synchronously require the module in Node.js.
In order to make use of the id
property added by the Babel plugin, you will need to create a manifest of assets keyed by this ID. An example of doing so can be found in sewing kit’s webpack-asset-metadata-plugin
package.
FAQs
Primitives for loading parts of an application asynchronously
The npm package @shopify/async receives a total of 46,432 weekly downloads. As such, @shopify/async popularity was classified as popular.
We found that @shopify/async demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 24 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.